home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
AOL File Library: 2,801 to 2,900
/
aol-file-protocol-4400-2801-to-2900.zip
/
AOLDLs
/
C++ Files Library
/
THINK Universal Headers Proje
/
THINK Univ Hdr ¹.sit
/
universal headers.c
next >
Wrap
C/C++ Source or Header
|
1994-02-06
|
3KB
|
64 lines
/*
THINK C Project for Universal Header support
by Joe Zobkiw
This project was created to prove to myself that I can use Apple's new
Universal Headers with THINK C (which does not ship with them.) If you
are a Metrowerks or MPW user you may already be using the Universal
Headers for PowerPC and 68k Macintosh. If you are still a THINK C user
and expect to easily be able to port your current programs to PowerPC
compilers in the future, you will want to use the Universal Headers
starting immediately. It's not _lots_ of work for an average application
but there are enough changes that you might as well start using the
new headers as soon as possible.
I am not going to describe the changes so please don't ask me. If you want
to know where to get these new headers, purchase ETO (Essential Tools & Objects)
from APDA (Apple Programmers & Developers Assoc) or purchase CodeWarrior from
Metrowerks (keyword: METROWERKS on AOL.) If you don't know the difference
between a pre-compiled header and a non-precompiled header and an MPW
.o format file then you shouldn't be using this. DO NOT send me email
saying "What are the Universal Headers?" Go eat some cookies instead. :o
I created this project file using a small shell application that I wrote.
I set up the options in the C and C++ options dialog boxes to compile my
sample app using the new Universal Headers and NO MACHEADERS. If you use
this project file to start your own projects you will have to #include
every file you use. This is not a bad thing since it makes you LEARN
where the toolbox functions you call are defined... :)
Note also that you must include (at least) Interface.o and Runtime.o.
These are the equivalent (more or less) of MacTraps in THINK. You may also
elect to include other .o files. As far as allowing THINK to access the
new header files themselves, I simply trashed all of the Apple #includes
that THINK provided and filled that folder with the new Universal Headers
instead. This should work fine.
I tested this with both a C and a C++ project and it compiled fine with the
current version (as of 2/6/94) of the Universal Header files. Since these
files may change in the future, this project might not work for the next
release of them...but in any case, it is a start and is not meant to be perfect.
Why did I create this? Because I'm starting a new application and I didn't
want to use MPW to write it since I don't like SADE. I don't yet trust
CodeWarrior and there are so many different versions of it that it's hard
to figure out what compiles what the correct way (however, the release version
will probably be killer, I'm sure! :) I'm used to THINK C and the THINK Debugger.
Since I can work well (and fast) in the THINK environment, I decided to use it
to write my initial code for this project. I can always convert it to CodeWarrior
later for PowerPC compilation (since I'm now using the Universal Headers :)
Please note that I am not supporting this project file in any way. If you have
short questions I MAY be able to answer them. Most of all this is for those people
who know what all this stuff means and want to use THINK C _NOW_ and not have
their work go to waste when they switch to another compiler for PowerPC development.
Joe Zobkiw (2/6/94)
America Online : AFL Zobkiw
Internet : aflzobkiw@aol.com
*/
main(void)
{
/* your program goes here */
}